Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NODE_LABEL Downstream Parameter needed/dodgy #2378

Closed
M-Davies opened this issue Jan 13, 2021 · 1 comment
Closed

NODE_LABEL Downstream Parameter needed/dodgy #2378

M-Davies opened this issue Jan 13, 2021 · 1 comment
Labels
bug Issues that are problems in the code as reported by the community duplicate Issues that are a duplicate of an issue in this (or another) repository investigate Issues that require extra investigation to calculate their purpose or goal jenkins Issues that enhance or fix our jenkins server

Comments

@M-Davies
Copy link
Contributor

Intially raised by Stewart on Slack -> https://adoptopenjdk.slack.com/archives/C09NW3L2J/p1610466417493400

There's a NODE_LABEL parameter to the individual build jobs and also a NODE_LABEL value in the BUILD_CONFIGURATION JSON. - two questions

  • Why do we need two (I'm guessing the separate one is needed for the scheduling? But then does it need to be in the build config? @johnoliver I'm hoping you could answer this one regarding this history of having both?
  • Sometimes if I go in and re-run a build job the NODE_LABEL parameter looks to be populated OK but after I submit it it seems to disappear and not schedule, re-running again copying the value from BUILD_CONFIGURATION seems to work ok. Is there a reason for this (weird jenkins quirk?) and does anyone know of a workaround? I (@M-Davies) suspect it's due to how we generate and instantiate this parameter but I can't be sure
@M-Davies M-Davies added bug Issues that are problems in the code as reported by the community jenkins Issues that enhance or fix our jenkins server investigate Issues that require extra investigation to calculate their purpose or goal labels Jan 13, 2021
@M-Davies
Copy link
Contributor Author

@M-Davies M-Davies added the duplicate Issues that are a duplicate of an issue in this (or another) repository label Jan 13, 2021
@karianna karianna modified the milestone: January 2021 Jan 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that are problems in the code as reported by the community duplicate Issues that are a duplicate of an issue in this (or another) repository investigate Issues that require extra investigation to calculate their purpose or goal jenkins Issues that enhance or fix our jenkins server
Projects
None yet
Development

No branches or pull requests

2 participants