Join GitHub today
[JENKINS-22637] ArtifactManager support #99
To handle symlinks and file attributes may require new core APIs—TBD. Really if you care about platform-specific stuff like this you should create a tarball and archive that instead, since you cannot guarantee that the Jenkins master will preserve these nuances. Similarly, suppressing of default excludes is desirable but might just be treated as a core bug fix, and again it is going to be safer and much more efficient to create a ZIP or tarball of all your little files.
I also plan to
but this will certainly require a new core baseline and might better be filed as an add-on PR.
Note that I am dropping the
I am also making an API change to
referenced this pull request
Feb 21, 2018
ikedam left a comment
Looks good to me.
@ikedam so I am leaving it up to your judgment what to do here. I noted the number of JIRA votes for various affected issues, to the extent that is meaningful data. This PR in isolation implements a feature with 14 votes (and no good workaround), and regresses three bug reports with a combined total of 14 votes (and the workaround of archiving a tarball rather than individual files). #100 implements the feature (and more) without regressing any of the prior bugs, but will require a new core baseline.
One option not previously discussed would be to merge this but release only as a
The hope is that once JEP-301 is deployed, Essentials users would get new stuff that just works, right away. Obviously a lot needs to happen before that is a reality.
@jglick Sorry for my late response.
This option looks good to me.
Let me have a little more time to work for https://issues.jenkins-ci.org/browse/JENKINS-47905 and https://issues.jenkins-ci.org/browse/JENKINS-47074.
Hmm... It seems that releasing 1.40 will mask 1.40-beta as described in https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/.
Updates center provides several versions of plugin lists for core versions by redirection.
But the experimental update center provides only one version, and will result 1.40-beta-1 inaccessible via the update center.
Anyway, that doesn't matter so much as users can download the beta version directly from http://updates.jenkins-ci.org/download/plugins/copyartifact/1.40-beta-1/copyartifact.hpi .