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

Set packaging defaults for Jenkins #8542

Merged
merged 1 commit into from
Oct 3, 2018

Conversation

andrewkroh
Copy link
Member

Control the defaults for Jenkins in our repo, but allow them to be
overridden by Jenkins parameters.

Control the defaults for Jenkins in our repo, but allow them to be
overridden by Jenkins parameters.
@andrewkroh
Copy link
Member Author

andrewkroh commented Oct 2, 2018

This will add back the -alpha1 to the snapshots produced by Jenkins from the master branch.

@andrewkroh
Copy link
Member Author

Copy link
Member

@ruflin ruflin left a comment

Choose a reason for hiding this comment

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

Change LGTM and build went green.

@@ -16,4 +16,10 @@ cleanup() {
}
trap cleanup EXIT

# This controls the defaults used the Jenkins package job. They can be
# overridden by setting them in the environement prior to running this script.
export BEAT_VERSION_QUALIFIER="${VERSION_QUALIFIER:-alpha1}"
Copy link
Member

Choose a reason for hiding this comment

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

So these values would be adjusted based on the branch?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, that would be the case. The alternative would be to put it in the JJB config in infra, but we want to get away from that model in order to have more control over our Jenkins jobs from our repo.

@andrewkroh andrewkroh merged commit 7f98aa2 into elastic:master Oct 3, 2018
@andrewkroh andrewkroh deleted the feature/jenkins-defaults branch November 8, 2018 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants