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

Update jenkins script for building packages #1805

Merged
merged 1 commit into from
Feb 14, 2025
Merged

Update jenkins script for building packages #1805

merged 1 commit into from
Feb 14, 2025

Conversation

LeiGlobus
Copy link
Contributor

Last few builds have failed due to some issues, this update (should) improve it.

After it's merged, I'll also update the default branch in Jenkins to main.

@LeiGlobus LeiGlobus added no-news-is-good-news This change does not require a news file quick-review Review of this should be quick and easy labels Feb 13, 2025
compute_endpoint/packaging/JenkinsFile Outdated Show resolved Hide resolved
Comment on lines 34 to 36
env.BRANCH_NAME = params.BRANCH_OR_TAG
env.BUILD_FOR_STABLE = params.BUILD_FOR_STABLE
env.TAG_NAME = "${env.BRANCH_NAME}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've forgotten the later-on Groovy script innards; would it behoove us to set one OR the other?

Meanwhile, if setting both (in direct answer to my question ☝️), perhaps clearer to colocate BRANCH_NAME and TAG_NAME since they're to be the same value. Consider:

env.BRANCH_NAME = params.BRANCH_OR_TAG
env.TAG_NAME = params.BRANCH_OR_TAG
env.BUILD_FOR STABLE = params.BUILD_FOR_STABLE

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same reason - I wasn't sure if TAG_NAME is used later, so left it set just in case. I made a bit more clearer as you suggested but I'll also look to see if TAG_NAME matters.

@LeiGlobus LeiGlobus merged commit 30d39dc into main Feb 14, 2025
21 checks passed
@LeiGlobus LeiGlobus deleted the jenkins311 branch February 14, 2025 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-news-is-good-news This change does not require a news file quick-review Review of this should be quick and easy
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants