Hello there, Recently, I finally rolled out this plugin for release 1.0.0
There is a problem when I'm doing *mvn release:prepare release:perform *I got below error: ace@acebuild:~/workspace/github/coordinator$ mvn release:prepare >> release:perform > > [INFO] Scanning for projects... > > [INFO] > > [INFO] >> ------------------------------------------------------------------------ > > [INFO] Building Coordinator Plugin 1.0.0-SNAPSHOT > > [INFO] >> ------------------------------------------------------------------------ > > .... > [INFO] [INFO] Copy webapp webResources to > /home/ace/workspace/github/coordinator/target/coordinator-1.0.0 [INFO] [INFO] Assembling webapp coordinator in > /home/ace/workspace/github/coordinator/target/coordinator-1.0.0 [INFO] [INFO] Generating hpi > /home/ace/workspace/github/coordinator/target/coordinator-1.0.0.hpi [INFO] [INFO] Building jar: > /home/ace/workspace/github/coordinator/target/coordinator-1.0.0.hpi [INFO] [INFO] > ------------------------------------------------------------------------ [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] > ------------------------------------------------------------------------ [INFO] [INFO] Total time: 1:14.099s [INFO] [INFO] Finished at: Thu Sep 18 12:33:22 EDT 2014 [INFO] [INFO] Final Memory: 36M/88M [INFO] [INFO] > ------------------------------------------------------------------------ ...... [INFO] Working directory: /home/ace/workspace/github/coordinator > > [INFO] Executing: /bin/sh -c cd /home/ace/workspace/github/coordinator && >> git push https://github.com/jenkinsci/coordinator-plugin.git >> coordinator-1.0.0 > > [INFO] Working directory: /home/ace/workspace/github/coordinator > > Username for 'https://github.com': *ace-han* > > Password for 'https://[email protected]': > > [INFO] >> ------------------------------------------------------------------------ > > [INFO] BUILD FAILURE > > [INFO] >> ------------------------------------------------------------------------ > > [INFO] Total time: 1:50.865s > > [INFO] Finished at: Thu Sep 18 13:27:41 EDT 2014 > > [INFO] Final Memory: 11M/28M > > [INFO] >> ------------------------------------------------------------------------ > > [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) >> on project coordinator: Unable to tag SCM > > [ERROR] Provider message: > > [ERROR] The git-push command failed. > > [ERROR] Command output: > > [ERROR] remote: Permission to jenkinsci/coordinator-plugin.git denied to >> ace-han. > > [ERROR] fatal: *unable to access >> 'https://github.com/jenkinsci/coordinator-plugin.git/ >> <https://github.com/jenkinsci/coordinator-plugin.git/>': The requested URL >> returned error: 403* > > > I should be the sole contributor for this repository now, but I could not push code to that repository, that's a little weird to me. My github user-id/password(ace-han/xxx) are different from jenkins-ci.org's (ace_jl_han/xxx) so I followed this wiki <https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins> and add my jenkins-ci.org acount info to ~/.m2/settings.xml and tried '*origin*' pointed to below 2 location respectively, and still got no luck [remote "origin"] > > url = [email protected]:jenkinsci/coordinator-plugin.git > > fetch = +refs/heads/*:refs/remotes/origin/* > > > [remote "origin"] > > url = [email protected]:ace-han/coordinator.git > > fetch = +refs/heads/*:refs/remotes/origin/* > > > [image: Inline image 1] My souce code lies in *https://github.com/ace-han/coordinator <https://github.com/ace-han/coordinator>, *and jenkins-ci forked repository is* https://github.com/jenkinsci/coordinator-plugin <https://github.com/jenkinsci/coordinator-plugin>* Wiki about this plugin:* https://wiki.jenkins-ci.org/display/JENKINS/Coordinator <https://wiki.jenkins-ci.org/display/JENKINS/Coordinator>* Could you help me through publishing this this version* release 1.0.0?* Thx in advance. Best Regards, Ace Han On Sun, Dec 16, 2012 at 6:20 PM, domi <[email protected]> wrote: > hi ace, > > don't get us wrong - we are looking forward for your contribution - but > this are the kind of questions a normal user would ask when searching > through > the list of plugins. It would be great if your documentation/wiki would > explain what the difference between your implementation and the others is. > There must be a reasons why you choosed to write your own plugin and not > to use/extend an existing one, what are the shortcomings of the other > plugins? - let the users know these reasons too. > > btw. nicolas forked your repo, so no reason to not enjoy your holidays :) > > /Domi > > > On 16.12.2012, at 10:01, Ace Han <[email protected]> wrote: > > Hello All, > > I'm surprised that this kind of plugin got so many comments. That > flattered me. > > I'm now taking a 7-day annual holiday. And found myself no access to the > working directory (even though I could, that would cost a great effort and > spoil this lovely holiday). > > I would be back on Dec 24, and share the code in giihub first. > > However, I sincerely hope that we could create a repository to host this > plugin. I'm pretty sure that this one would interest you for coordination > of jobs in jenkns <338.gif> > > Best Regards, > Ace > > > On Sat, Dec 15, 2012 at 10:24 PM, nicolas de loof < > [email protected]> wrote: > >> join plugin has a limited scope, so I won't include it here >> >> build-pipeline is only about visualization of a static flow (job order >> don't change) >> >> multijob is to establish such a static flow (if I understood it right) >> >> build-flow can be used to make the flow completely context-specific, so >> that two subsequent runs won't trigger same jobs / order. >> it compares with jenkow, with a significantly distinct implementation >> >> So, I think all those plugin make sense for distinct use-cases, would >> like to know more about this one to understand how it fit this growing "job >> orchestration ecosystem" >> >> >> 2012/12/15 domi <[email protected]> >> >>> This looks nice, but what is the difference to plugins like: >>> >>> - https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin >>> - https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin >>> - https://wiki.jenkins-ci.org/display/JENKINS/Join+Plugin >>> - https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin >>> >>> although these plugins do it different, it seems that all of these >>> plugins try to solve the same issue: coordination of jobs >>> >>> /Domi >>> >>> On 13.12.2012, at 10:00, Ace Han <[email protected]> wrote: >>> >>> Hello, >>> >>> We have been working on a new Jenkins plugin, which coordinates children >>> jobs defined within to be executed in a serial or parallel pattern >>> according to user-defined order >>> >>> This is the github: git://github.com/a >>> <http://github.com/vanderhallenf/eloyente.git>ce-han/coordinator >>> >>> Draft version is done, but would like to do some code refactor to make >>> it beautiful^_^ >>> >>> Attachment a snapshot for your reference. >>> >>> <https://lh5.googleusercontent.com/-tlPAjoOq0ZU/UMmY72jQ2BI/AAAAAAAAAAw/drfyq3VRjlA/s1600/demo.png> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> Is it possible to create a repository to host this plugin? >>> >>> Best regards, >>> Ace >>> >>> >>> >> > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
