Red Hat Bugzilla – Bug 1020188
force_clean_build marker does not work with jenkins builds
Last modified: 2015-05-14 19:30:26 EDT
Description of problem:
Given an app with a Jenkins client added, the force_clean_build marker does not with its Jenkins builds. On the other hand, when removing the Jenkins client, force clean build works again.
This problem happens to Ruby cartridges only before Sprint 35 (https://bugzilla.redhat.com/show_bug.cgi?id=1005123), and now all web carts are affected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create an app with Jenkins client added
2. install some dependencies to the app
3. check the Jenkins build log
4. create a force_clean_build and trigger another Jenkins build
5. check the log of the build in Step 4, to confirm if the dependencies in Step 2 are reinstalled
6. remove the Jenkins client and trigger a third Jenkins build
Take a JBossAS application as an example, in Step 3, we can see that the app was downloading and installing packages in its build. Moreover, in Step 5, the app was not reinstalling the packages in Step 2 even with the presence of a force_clean_build marker. The force_clean_build marker, however, works again after removing the Jenkins client from the app.
force_clean_build should work with Jenkins builds
*** Bug 1005123 has been marked as a duplicate of this bug. ***
Commit pushed to master at https://github.com/openshift/origin-server
Sync deployment metadata from jenkins builder
Write deployment metadata during build
Sync metadata from jenkins builder gear back upstream
Create new deployment directory for each jenkins build
Commit pushed to master at https://github.com/openshift/li
Update jenkins_shell_command to create a new deployment directory for
each build and to record deployment metadata (git info, force clean
build, hot deploy) that will be synced back to the upstream gear.
Verified in devenv_3921.
After creating a force_clean_build marker, the dependencies are installed again:
Fetching gem metadata from http://rubygems.org/..........
Installing rack (1.5.2)
Installing ref (1.0.5)
Using bundler (1.1.4)
Your bundle is complete! It was installed into ./vendor/bundle