Details

    • Similar Issues:

      Description

      Hi,

      Is Jenkins can build the job using more than one repo (like repo1, repo2, ..  all changed need to be included in one build) and with same branch using TOPIC.

      Here is the more explanation:

      We use "repo sync" to pull the latest changes from dev branch (it is based on manifest file how we configure) from our host repository. My requirement is something like below:

      $ cd <WORKING_DIR1>

      $ repo sync

      $ cd <repo1>

      made some change, add and then push to gerrit using topic called "new-updates"

      $ cd ../<repo2>

      In repo2 also made some change, add and then push to gerrit using the same topic called "new-updates" . (So I pushed changes of repo1 and repo2 into gerrit using the same topic called "new-updates")

      My requirement:

      Here my requirement is Jenkins needs to trigger the build from gerrit using repo1 and repo2 changes (by using TOPIC called "new-updates"). I know Jenkins can trigger the build using one repo but I want Jenkins should use two changes (from repo1 and repo2) in one build using topic.

      Can you let me know if there is any such solution.

      Thanks

      Laxma

        Attachments

          Activity

          Hide
          lucamilanesio Luca Domenico Milanesio added a comment -

          Thank you for raising this: the current plugin is tightly coupled at the moment with the Jenkinsfile pipelines, which are tried to a single repository.

          I believe your use-case would still make sense if a top-level repository (i.e. the super-project) would be used as common collector of all changes across repositories. Then the top-level repository could have a Jenkinsfile associated and that could get the subprojects tied to a topic.

          What do you think?

          Show
          lucamilanesio Luca Domenico Milanesio added a comment - Thank you for raising this: the current plugin is tightly coupled at the moment with the Jenkinsfile pipelines, which are tried to a single repository. I believe your use-case would still make sense if a top-level repository (i.e. the super-project) would be used as common collector of all changes across repositories. Then the top-level repository could have a Jenkinsfile associated and that could get the subprojects tied to a topic. What do you think?
          Hide
          inegm Islam Negm added a comment - - edited

          Luca Domenico Milanesio

          Hello Luca, 

          I wonder if this is supported now, do you have any updates about this topic?

          Thanks in advance.

          Edit#1: I've also changed the ticket priority to be blocker, as in my team we're working with this paradigm mentioned in the ticket description and we want to add the Jenkins verification functionality to the sub-module code review. And this is crucial for us to move on. 

          Show
          inegm Islam Negm added a comment - - edited Luca Domenico Milanesio Hello Luca,  I wonder if this is supported now, do you have any updates about this topic? Thanks in advance. Edit#1: I've also changed the ticket priority to be blocker, as in my team we're working with this paradigm mentioned in the ticket description and we want to add the Jenkins verification functionality to the sub-module code review. And this is crucial for us to move on. 
          Hide
          lucamilanesio Luca Domenico Milanesio added a comment -

          I believe this is more a problem on the multi-branch pipeline concept in Jenkins: where would the Jenkinsfile be stored? one repo? both? Where would you fetch the pipelines from?

          Show
          lucamilanesio Luca Domenico Milanesio added a comment - I believe this is more a problem on the multi-branch pipeline concept in Jenkins: where would the Jenkinsfile be stored? one repo? both? Where would you fetch the pipelines from?

            People

            • Assignee:
              lucamilanesio Luca Domenico Milanesio
              Reporter:
              lrdy_scm Laxma Reddy
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: