[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-37503 Add Pipeline Support for ArtifactDeployer Change By: Jason Davis Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title Jason Davis commented on JENKINS-37503 Re: Add Pipeline Support for ArtifactDeployer Just trying to understand, it sounds like there currently isn't a way to post to remote shares and still build the "Last Successful Deployed Artifacts" link in the Jenkins job pages with the plugin. Is that true? For me, very few of the jobs utilize maven and everyone I support is used to seeing remote artifacts deployed in the Freestyle jobs and then downloading artifacts using the "Last Successful Deployed Artifacts" links the plugin creates in the Job pages. If I can't replicate that in a pipeline, this becomes a blocker, because I can't convert the jobs from Freestyle ones. I really don't want to use the built-in Archive the Artifacts" step, because this plugin's great advantage over that feature, is that big installers, etc. can be posted to a separate server and not on the Jenkins master which for me will seriously increase the storage/backup requirements for the master. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title Clint Chapman commented on JENKINS-37503 Re: Add Pipeline Support for ArtifactDeployer I obviously haven't used it yet. That is a problem. Thanks for the pointer. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title Jo Vandeginste commented on JENKINS-37503 Re: Add Pipeline Support for ArtifactDeployer I'm aware, but we hit this: https://issues.jenkins-ci.org/browse/JENKINS-38272 (Also, I clearly assumed you were talking about maven repo's, so my workaround is probably not that useful for you ...) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title Clint Chapman commented on JENKINS-37503 Re: Add Pipeline Support for ArtifactDeployer Thanks Jo. Not quite as straight-forward as I'd like... We just want to deploy .NET projects to a file share and have them show up as artifacts on the job. Not sure if you're aware but I believe pipeline global libraries are automatically approved and avoid sandboxing. Thanks again Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title
Jo Vandeginste edited a comment on JENKINS-37503
Re: Add Pipeline Support for ArtifactDeployer
Only by re-implementing the functionality (what I did for our projects); basically I run:{code}mvn deploy:deploy-file -f ${deployPomFile} -DpomFile=${deployPomFile} \-Dfile=${file} -DrepositoryId=${remoteRepository} \-Durl=sftp://${remoteUploadUser}@${remoteServer}:${remoteLocation}{code}Where:* ${ deployPomFile } : the (self-generated) pom.xml containing extra information about the target server + wagon-ssh* ${ file } : the jar or war file to be published* ${ remoteRepository } : the ID of the repository (as found in settings.xml and/or pom.xml)* ${ remoteUploadUser } , ${ remoteServer } , ${ remoteLocation } : the remote (ssh/sftp) user, server and root directory where the artifact should be uploaded toBasically I write a second pom.xml with the relevant information from the real pom.xml (modelVersion, groupId, artifactId, version, packaging) and use this template (to support uploading via ssh/sftp/scp):{code:xml} xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> ${modelVersion} ${groupId} ${artifactId} ${version} ${packaging}org.apache.maven.wagonwagon-ssh2.10{code}There is probably a cleaner way to do this, but the Jenkins sandbox is limiting :-)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title
Jo Vandeginste edited a comment on JENKINS-37503
Re: Add Pipeline Support for ArtifactDeployer
Only by re-implementing the functionality (what I did for our projects); basically I run:{code :sh }mvn deploy:deploy-file -f ${deployPomFile} -DpomFile=${deployPomFile} \-Dfile=${file} -DrepositoryId=${remoteRepository} \-Durl=sftp://${remoteUploadUser}@${remoteServer}:${remoteLocation}{code}Where:* ${deployPomFile} : the (self-generated) pom.xml containing extra information about the target server + wagon-ssh* ${file}: the jar or war file to be published* ${remoteRepository} : the ID of the repository (as found in settings.xml and/or pom.xml)* ${remoteUploadUser}, ${remoteServer}, ${remoteLocation} : the remote (ssh/sftp) user, server and root directory where the artifact should be uploaded toBasically I write a second pom.xml with the relevant information from the real pom.xml (modelVersion, groupId, artifactId, version, packaging) and use this template (to support uploading via ssh/sftp/scp):{code:xml} xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> ${modelVersion} ${groupId} ${artifactId} ${version} ${packaging}org.apache.maven.wagonwagon-ssh2.10{code}There is probably a cleaner way to do this, but the Jenkins sandbox is limiting :-)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title
Jo Vandeginste edited a comment on JENKINS-37503
Re: Add Pipeline Support for ArtifactDeployer
Only by re-implementing the functionality (what I did for our projects); basically I run:{code: bash sh }mvn deploy:deploy-file -f ${deployPomFile} -DpomFile=${deployPomFile} \-Dfile=${file} -DrepositoryId=${remoteRepository} \-Durl=sftp://${remoteUploadUser}@${remoteServer}:${remoteLocation}{code}Where:* ${deployPomFile} : the (self-generated) pom.xml containing extra information about the target server + wagon-ssh* ${file}: the jar or war file to be published* ${remoteRepository} : the ID of the repository (as found in settings.xml and/or pom.xml)* ${remoteUploadUser}, ${remoteServer}, ${remoteLocation} : the remote (ssh/sftp) user, server and root directory where the artifact should be uploaded toBasically I write a second pom.xml with the relevant information from the real pom.xml (modelVersion, groupId, artifactId, version, packaging) and use this template (to support uploading via ssh/sftp/scp):{code:xml} xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> ${modelVersion} ${groupId} ${artifactId} ${version} ${packaging}org.apache.maven.wagonwagon-ssh2.10{code}There is probably a cleaner way to do this, but the Jenkins sandbox is limiting :-)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title
Jo Vandeginste edited a comment on JENKINS-37503
Re: Add Pipeline Support for ArtifactDeployer
Only by re-implementing the functionality (what I did for our projects); basically I run:{ noformat code:bash }mvn deploy:deploy-file -f ${deployPomFile} -DpomFile=${deployPomFile} \-Dfile=${file} -DrepositoryId=${remoteRepository} \-Durl=sftp://${remoteUploadUser}@${remoteServer}:${remoteLocation}{ noformat code }Where:* ${deployPomFile}: the (self-generated) pom.xml containing extra information about the target server + wagon-ssh* ${file}: the jar or war file to be published* ${remoteRepository}: the ID of the repository (as found in settings.xml and/or pom.xml)* ${remoteUploadUser}, ${remoteServer}, ${remoteLocation}: the remote (ssh/sftp) user, server and root directory where the artifact should be uploaded toBasically I write a second pom.xml with the relevant information from the real pom.xml (modelVersion, groupId, artifactId, version, packaging) and use this template (to support uploading via ssh/sftp/scp):{ noformat code:xml } xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> ${modelVersion} ${groupId} ${artifactId} ${version} ${packaging}org.apache.maven.wagonwagon-ssh2.10{ noformat code }There is probably a cleaner way to do this, but the Jenkins sandbox is limiting :-)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title
Jo Vandeginste commented on JENKINS-37503
Re: Add Pipeline Support for ArtifactDeployer
Only by re-implementing the functionality (what I did for our projects); basically I run:
mvn deploy:deploy-file -f ${deployPomFile} -DpomFile=${deployPomFile} \
-Dfile=${file} -DrepositoryId=${remoteRepository} \
-Durl=sftp://${remoteUploadUser}@${remoteServer}:${remoteLocation}
Where:
$ {deployPomFile} : the (self-generated) pom.xml containing extra information about the target server + wagon-ssh
$ {file} : the jar or war file to be published
$ {remoteRepository} : the ID of the repository (as found in settings.xml and/or pom.xml)
$ {remoteUploadUser} , $ {remoteServer} , $ {remoteLocation} : the remote (ssh/sftp) user, server and root directory where the artifact should be uploaded to
Basically I write a second pom.xml with the relevant information from the real pom.xml (modelVersion, groupId, artifactId, version, packaging) and use this template (to support uploading via ssh/sftp/scp):
${modelVersion}
${groupId}
${artifactId}
${version}
${packaging}
org.apache.maven.wagon
wagon-ssh
2.10
There is probably a cleaner way to do this, but the Jenkins sandbox is limiting
Add Comment
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title Clint Chapman commented on JENKINS-37503 Re: Add Pipeline Support for ArtifactDeployer Is there a workaround for using this plugin in pipeline without native support? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title Marc Vollmer created an issue Jenkins / JENKINS-37503 Add Pipeline Support for ArtifactDeployer Issue Type: New Feature Assignee: Gregory Boissinot Components: artifactdeployer-plugin Created: 2016/Aug/18 9:06 AM Priority: Minor Reporter: Marc Vollmer Since Jenkins 2.0 we are moving our Freestyle Builds to Pipelines, it would be nice to have Pipeline support in the ArtifactDeployer to not do this manually. Add Comment This message was sent by Atlassian JIRA
