Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9342

Add "Use View Mask for ChangeLog" Option

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None

      Description

      An option that uses the View Mask for the changelog would be beneficial to those who wish to limit email notifications to those who have changed files of interest, but still sync the full workspace.

        Activity

        Hide
        barnish Andrew Barnish added a comment -

        Is this difficult to implement?

        It would be useful to have this feature as I'm trying to setup Jenkins to build only when the dependencies of a job target change.
        Unfortunately the workspace view often contains more files then are necessary to build the target, so I'm intending to auto-generate the dependency list each time a job builds and use it to update the Perforce ViewMask used for polling.
        The same ViewMask should be used for the ChangeLog and sending email notifications.

        Show
        barnish Andrew Barnish added a comment - Is this difficult to implement? It would be useful to have this feature as I'm trying to setup Jenkins to build only when the dependencies of a job target change. Unfortunately the workspace view often contains more files then are necessary to build the target, so I'm intending to auto-generate the dependency list each time a job builds and use it to update the Perforce ViewMask used for polling. The same ViewMask should be used for the ChangeLog and sending email notifications.
        Hide
        rpetti Rob Petti added a comment -

        This is only for the changelog and email notifications to culprits. Using the view mask for polling as you describe is already possible.

        Show
        rpetti Rob Petti added a comment - This is only for the changelog and email notifications to culprits. Using the view mask for polling as you describe is already possible.
        Hide
        chelusly Chelu Sly added a comment -

        I would like to see this option implemented. I believe it would give the user fine tuning when it comes to seeing the set of changes for a given build.

        If the user has multiple branch specs defined within the client view map then all changes from the client view are displayed within the changelog. At our company we have hundreds of devs working 24/7 and the change log can become massive.

        Example:

        Client Workspace View:
        //demo/test/sw/01.0/trunk/...
        //demo/common_libs/sw/01.0/trunk/...

        Add option for "Use View mask Polling:
        //demo/test/sw/01.0/trunk/...

        Trigger a build if source changes are made to the demo-test-trunk project.

        The build will poll and syncs properly. The problem exist that the changelog will show all all the changes from the branch specs listed within the client workspace. We only want to see the changes that triggered the build, i.e. the view mask we are using for polling.

        As of right now I'm having to create a separate setup job with a single branch location using the view mask polling and syncing options. I'm then having to sync all the other locations by hand during the build. This allows me to fine tune what's changes are being seen within the changelog. This is a kludgy alternative but works for now.

        It would truly be nice to have the option "Use View Mask for ChangeLog" or to be able to exclude branches from the changelog.

        Show
        chelusly Chelu Sly added a comment - I would like to see this option implemented. I believe it would give the user fine tuning when it comes to seeing the set of changes for a given build. If the user has multiple branch specs defined within the client view map then all changes from the client view are displayed within the changelog. At our company we have hundreds of devs working 24/7 and the change log can become massive. Example: Client Workspace View: //demo/test/sw/01.0/trunk/... //demo/common_libs/sw/01.0/trunk/... Add option for "Use View mask Polling: //demo/test/sw/01.0/trunk/... Trigger a build if source changes are made to the demo-test-trunk project. The build will poll and syncs properly. The problem exist that the changelog will show all all the changes from the branch specs listed within the client workspace. We only want to see the changes that triggered the build, i.e. the view mask we are using for polling. As of right now I'm having to create a separate setup job with a single branch location using the view mask polling and syncing options. I'm then having to sync all the other locations by hand during the build. This allows me to fine tune what's changes are being seen within the changelog. This is a kludgy alternative but works for now. It would truly be nice to have the option "Use View Mask for ChangeLog" or to be able to exclude branches from the changelog.
        Hide
        scm_issue_link SCM/JIRA link daemon added a comment -

        Code changed in jenkins
        User: Rob Petti
        Path:
        src/main/java/hudson/plugins/perforce/PerforceSCM.java
        src/main/resources/hudson/plugins/perforce/PerforceSCM/config.jelly
        src/main/webapp/help/useViewMaskForChangeLog.html
        http://jenkins-ci.org/commit/perforce-plugin/3de2bc83b884f68027f523375674163137ff2040
        Log:
        [FIXED JENKINS-9342] using the view mask for the changelog is now a separate option

        Show
        scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Rob Petti Path: src/main/java/hudson/plugins/perforce/PerforceSCM.java src/main/resources/hudson/plugins/perforce/PerforceSCM/config.jelly src/main/webapp/help/useViewMaskForChangeLog.html http://jenkins-ci.org/commit/perforce-plugin/3de2bc83b884f68027f523375674163137ff2040 Log: [FIXED JENKINS-9342] using the view mask for the changelog is now a separate option

          People

          • Assignee:
            Unassigned
            Reporter:
            rpetti Rob Petti
          • Votes:
            6 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: