Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

As part of release-3.7.0, all configuration access in jenkins, rancher and VM’s are removed for everyone working on sunbird. This will require some changes in the jenkinsfile code. Please refer to these PR’s for information on how to update your build jenkinsfiles.

https://github.com/project-sunbird/sunbird-core-dataproducts/pull/107
https://github.com/project-sunbird/knowledge-platform/pull/538
https://github.com/Sunbird-Ed/SunbirdEd-portal/pull/5997
https://github.com/project-sunbird/sunbird-lms-service/pull/691

None of the staging automated jenkins files need this change. The staging automated jenkins files are named as auto_build_deploy

With the new change, the build job looks like this -

In the paramater called github_release_tag the default value will be refs/heads/${public_repo_branch}

${public_repo_branch} will always point to latest release version. As of today, it release-3.7.0.

Even with this change, polling scm works and any new commits merged to the release branches will be auto built and deployed.

There are some points to be noted here on the SCM polling and how it works -

Release propagation:

  • The first build of a release must be triggered manually.

  • When we move to release-3.8.0, the value of ${public_repo_branch} will be release-3.8.0. But any PR merges or commits will not be auto built and deployed automatically.

  • The PR owner (very first PR of the release branch) has to trigget the job manually by clicking Build with Parameters. You don't have to change the refs/heads/${public_repo_branch} as ${public_repo_branch} will already be pointing to release-3.8.0. Just build the job.

  • Once the first commit of a release branch is built, any new commits or PR merges will be automatically built.

Hotfixes propagation:

  • Again this flow also follows the same principle, but requires an additional step.

  • Lets say we are in release-3.7.0 and you want to send a hotifx to release-3.6.0.

  • You would like to test this hotfix first in dev before sending to preprod / prod.

  • In that case, you can go to the jenkins job (AFTER YOUR PR IS MERGED, since you cannot use your forked repos anymore), change the value of refs/heads/${public_repo_branch} to refs/heads/release-3.6.0 and then build the job.

  • You are happy your fix is working, but you have stopped all automated builds of your job. Since now the SCM polling will keep checking release-3.6.0 branch for new commits to be built automatically.

  • You need to ensure that after you verify your fix in dev, go back to the job and run the job again with the latest release branch using refs/heads/${public_repo_branch}.

  • Or else your team mates latest release changes will not be auto built and deployed.

  • This is the responsibility of the developer who works on the hotfix. He has to revert back the dev environment to latest release version after verifying the hotfix.

Sunbird Adopters Use Case:

  • In terms of adopter use, no functionality has changed. Except we will ship the config files with the default value as refs/tags/${public_repo_branch} instead of refs/heads/${public_repo_branch} since adopters always use tags to build their tag.

  • For Diksha or any other other adopter who usually builds on RC tags, they will use something like this refs/tags/release-3.7.0_RC1

  • Even just using release-3.7.0_RC1 will work. This will not work only when we have a branch and tag both with same name.

  • No labels