Make Jenkinsfile multi-branch pipeline compatible #190
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The multi-branch pipelines can give us ability to discover and run jobs against all branches and PRs. Which means we don't need to provide job parameters for a custom source: - Remove the REPO_URL and REPO_BRANCH parameters - Remove the Source stage Additional optimizations: - Use more generic labels for Jenkins agents - Use short names for the main stages Signed-off-by: Elkhan Mammadli <elkhan.mammadli@protonmail.com>
andrewlukoshko
pushed a commit
that referenced
this pull request
Jan 8, 2024
* Get, download and install latest almalinux-gpg-keys package when migrating from CentOS Stream9 Fixes: #183 * Add 'epel-next-release' to the list of OS specific packages need to be removed. Fixes: #184 * Add 'evolution-data-server-ui' to the list of OS specific packages need to be removed. Fixes: #182 * Make Jenkinsfile multi-branch pipeline compatible (#190) The multi-branch pipelines can give us ability to discover and run jobs against all branches and PRs. Which means we don't need to provide job parameters for a custom source: - Remove the REPO_URL and REPO_BRANCH parameters - Remove the Source stage Additional optimizations: - Use more generic labels for Jenkins agents - Use short names for the main stages Signed-off-by: Elkhan Mammadli <elkhan.mammadli@protonmail.com> * Increase stage timeout to 60 minutes The 20 minutes timeout per stage is not flexible for the Jenkis agents with different hardware and internet connection speeds. Especially on the legacy versions it can took much more time than 20 minutes. Let's increase it to 60 minutes and see how it works. Signed-off-by: Elkhan Mammadli <elkhan.mammadli@protonmail.com> * Get, download and install latest almalinux-gpg-keys package when migrating from CentOS Stream9 Fixes: #183 --------- Signed-off-by: Elkhan Mammadli <elkhan.mammadli@protonmail.com> Co-authored-by: Elkhan Mammadli <elkhan.mammadli@protonmail.com> Co-authored-by: Eduard Abdullin <55892454+eabdullin1@users.noreply.github.com> Co-authored-by: Yuriy Kohut <ykohut@onapp.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The multi-branch pipelines can give us ability to discover and run jobs against all branches and PRs.
Which means we don't need to provide job parameters for a custom source:
Additional optimizations: