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

CIFS publisher doesn't provide links to artifacts

    XMLWordPrintable

Details

    Description

      Most if not all of the artifact publisher plugins for Jenkins provide links directly on the dashboard pointing to the artifacts that were published. All, except for the CIFS publisher that is. This inconsistency makes it hard for people to interact with artifacts via the Jenkins dashboard as there is no easy correlation between artifacts found on a network share and the CI job that created them. This should be fixed sooner rather than later.

      Attachments

        Activity

          Providing a screen shot of what the artifact links look like when using the built in artifact manager plugin in Jenkins. Ideally the CIFS plugin would mirror this behavior.

          leedega Kevin Phillips added a comment - Providing a screen shot of what the artifact links look like when using the built in artifact manager plugin in Jenkins. Ideally the CIFS plugin would mirror this behavior.
          slide_o_mix Alex Earl added a comment -

          How would you link to a CIFS share? The artifacts shown in the screenshot are archived internally to Jenkins and thus can be served by Jenkins. 

          slide_o_mix Alex Earl added a comment - How would you link to a CIFS share? The artifacts shown in the screenshot are archived internally to Jenkins and thus can be served by Jenkins. 
          justinnimmo Justin Nimmo added a comment - - edited

          Please review this issue again.  Even a link to the drop location of the assemblies would be to the users advantage.  End users do not have access to the management area to see where the initial drop location is pointing.  A simple link in the build output properties would go a long way.

          Example image attached.

          justinnimmo Justin Nimmo added a comment - - edited Please review this issue again.  Even a link to the drop location of the assemblies would be to the users advantage.  End users do not have access to the management area to see where the initial drop location is pointing.  A simple link in the build output properties would go a long way. Example image attached.

          For your information, all publish-over-cifs component type JENKINS issues related to the Publish Over CIFS plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues

          Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues/70
          And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-cifs-plugin/issues?q=%22JENKINS-32962%22

          (Note: this is an automated bulk comment)

          gmcdonald Gavin McDonald added a comment - For your information, all publish-over-cifs component type JENKINS issues related to the Publish Over CIFS plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues/70 And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-cifs-plugin/issues?q=%22JENKINS-32962%22 (Note: this is an automated bulk comment)

          This issue has been closed - please see the new Github Issue for this in the previous comment.

          gmcdonald Gavin McDonald added a comment - This issue has been closed - please see the new Github Issue for this in the previous comment.

          People

            Unassigned Unassigned
            leedega Kevin Phillips
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: