Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-508

when building a PR, use a private branch instead of crw-2.0-rhel-8

XMLWordPrintable

      22:58:38 [INFO] Download https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/crw_master_PR/lastSuccessfulBuild/artifact/codeready-workspaces/assembly/codeready-workspaces-assembly-main/target/codeready-workspaces-assembly-main.tar.gz:
      ...
      22:58:44 + [[ [crw-2.0-rhel-8 fefa007] [get sources] Update from Jenkins :: crw_master_PR ::  Build #11 (2019-11-21 22:23:41 EST) :: che-dev @ ea65 (20) :: che-parent @ 3348 (7.3.2) :: che-ls-jdt @ 288b (0.0.3) :: che @ 29d13 (7.3.2) :: codeready-workspaces @ 9433 (2.0.0.GA) :: codeready-workspaces-assembly-main.tar.gz
      22:58:44  2 files changed, 7 insertions(+), 5 deletions(-)
      ...
      22:58:45 + git push
      ...
      22:58:49 remote: * Publishing information for 1 commits        
      22:58:49 To ssh://crw-build@pkgs.devel.redhat.com/containers/codeready-workspaces
      22:58:49    4a06945..fefa007  crw-2.0-rhel-8 -> crw-2.0-rhel-8
      ...
      22:58:49 [INFO] Trigger container-build in current branch: rhpkg container-build --scratch
      ...
      22:58:51 Created task: 24881112
      22:58:51 Task info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=24881112
      ...
      23:02:22 2019-11-22 04:02:16,507 platform:- - atomic_reactor.plugins.tag_from_config - DEBUG - Using additional unique tag rh-osbs/codeready-workspaces-server-rhel8:crw-2.0-rhel-8-containers-candidate-89319-20191122035915
      
      

      One problem with this new approach is that the above commit is in the crw-2.0-rhel-8 branch, not a scratch branch. So we should fix that so that we're not muddling the waters in the 2.0 branch.

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: