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

find better way to release 2.0 #293

Closed
vdelendik opened this issue Apr 4, 2023 · 1 comment
Closed

find better way to release 2.0 #293

vdelendik opened this issue Apr 4, 2023 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@vdelendik
Copy link
Contributor

vdelendik commented Apr 4, 2023

most of our management jobs uses master branch. Due to the breaking change in jenkins jobdsl (#273) we seems like can't merge to master latest changes. But better to test using such scenario:

  1. setup CE using master branch (v2.2)
  2. update all Management_Jobs pipelines replacing master to develop:
@Library('Zebrunner-CE@master')
->
@Library('Zebrunner-CE@develop')
  1. test that such updated jobs work correctly:
    RegisterOrganization
    RegisterReportingCredentials
    RegisterHubCredentials
    RegisterMavenSettings
    DeleteOrganization

if all good with these jobs and management jobs can generate content using previous pipeline-ce v1.8 we can merge to master and branch to 2.0

@vdelendik vdelendik added the enhancement New feature or request label Apr 4, 2023
@vdelendik vdelendik added this to the 2.0 milestone Apr 4, 2023
@vdelendik
Copy link
Contributor Author

all good we can merge to master but in general it has sense:

  1. keep master as is.
  2. Make main as default one
  3. merge develop to main
  4. update all management jobs in jenkins to use main starting from the next release.

it should guarantee 100% compatibility for the existing CE environments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

1 participant