I've been wondering the same thing but I am not sure. I wonder if there is
any sort of log on the server that someone with those privileges could look
at. I'm out of ideas sadly.

On Sat, Jan 14, 2017, 07:09 Irfan Sayed <irfu.sa...@gmail.com> wrote:

> When i requested initially for hosting plugin in jenkins-ci org, following
> was the original discussion:
> https://issues.jenkins-ci.org/browse/HOSTING-59
>
> we had changed the JIRA component and plugin name to align the proper
> artifactID and all.
> is this issue due to this ?
>
> Regards,
>
>
> On Sat, Jan 14, 2017 at 7:25 PM, Irfan Sayed <irfu.sa...@gmail.com> wrote:
>
> Yes i do have SNAPSHOT version in the POM.
> mvn deploy command also failing with the same error ..
> i am still not getting what is the issue
>
> regards,
>
>
> On Sat, Jan 14, 2017 at 7:14 PM, Slide <slide.o....@gmail.com> wrote:
>
> If your version has SNAPSHOT in it, you don't need to add anything.
> Snapshots are automatically deployed to the correct place I believe.
>
> On Sat, Jan 14, 2017, 05:52 Irfan Sayed <irfu.sa...@gmail.com> wrote:
>
> OK. i made the POM changes in my plugin and added following:
> <distributionManagement>
>    <snapshotRepository>
>        <id>propSnap</id>
>         <url>https://repo.jenkins-ci.org/snapshots</url>
>
>     </snapshotRepository>
>     <repository>
>          <id>propRel</id>
>          <url>https://repo.jenkins-ci.org/releases</url>
>         </repository>
>   </distributionManagement>
>
> run the same command: mvn clean package deploy
> same error : "401 unauthorized"
>
> regards,
>
>
> On Sat, Jan 14, 2017 at 1:46 AM, Baptiste Mathus <m...@batmat.net> wrote:
>
> Also, quick tip: you can stop trying to release, but only do "mvn deploy"
> to see if you can deploy snapshots, because this is the thing that is
> failing for you. Github pushes seem to work, only artifacts have an in
> issue IIUC.
>
> Le 14 janv. 2017 9:59 AM, "Irfan Sayed" <irfu.sa...@gmail.com> a écrit :
>
> Yes . i am able to login to :
> https://accounts.jenkins.io/login?from=%2Fmyself%2F
> i uploaded public key as well on above link and tried again releasing.
> but still the same error
>
> Regards,
>
>
> On Sat, Jan 14, 2017 at 3:59 AM, Slide <slide.o....@gmail.com> wrote:
>
> Oh, I missed your message about the typo before I hit send. Are you able
> to login to https://accounts.jenkins.io/login?from=%2Fmyself%2F with the
> username/password combo that you have in your settings.xml?
>
> On Fri, Jan 13, 2017, 15:17 Slide <slide.o....@gmail.com> wrote:
>
> From the same console, can you do something like this:
>
>
> https://help.github.com/articles/testing-your-ssh-connection/
>
>
> On Fri, Jan 13, 2017 at 12:55 PM Irfan Sayed <irfu.sa...@gmail.com> wrote:
>
> made the scm section changes and committed.
> here is the build output log:
>
> ef-builder ---
>     [INFO] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>                                               .hpi to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.hpi
>     [INFO] Installing C:\sinatra-chef-builder-plugin\pom.xml to
> C:\Users\irfanjs
>
> \.m2\repository\org\jenkins-ci\plugins\sinatra-chef-builder\1.10\sinatra-chef-bu
>                                                               ilder-1.10.pom
>     [INFO] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>                                               .jar to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.jar
>     [INFO]
> ---------------------------------------------------------------------
>                                                         ---
>     [INFO] BUILD SUCCESS
>     [INFO]
> ---------------------------------------------------------------------
>                                                         ---
>     [INFO] Total time: 02:35 min
>     [INFO] Finished at: 2017-01-13T11:36:47-08:00
>     [INFO] Final Memory: 62M/167M
>     [INFO]
> ---------------------------------------------------------------------
>                                                         ---
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git status --porcelain ."
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? release.properties
> [WARNING] Ignoring unrecognized line: ?? target/
> [INFO] Executing: cmd.exe /X /C "git commit --verbose -F
> C:\Users\irfanjs\AppDat
>           a\Local\Temp\maven-scm-1195565814.commit pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git push
> g...@github.com/jenkinsci/sinatra-chef-
>                             builder-plugin.git
> refs/heads/master:refs/heads/master"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 03:37 min
> [INFO] Finished at: 2017-01-13T11:36:48-08:00
> [INFO] Final Memory: 16M/39M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5
>                                     .3:prepare (default-cli) on project
> sinatra-chef-builder: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'g...@github.com/jenkinsci/sinatra-chef-builder-plugin.git'
> does n                                                               ot
> appear to be a git repository
> [ERROR] fatal: Could not read from remote repository.
> [ERROR]
> [ERROR] Please make sure you have the correct access rights
> [ERROR] and the repository exists.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e swit                                                               ch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please rea                                                               d
> the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
>                                                     eption
>
> irfanjs@host-10 MINGW64 /c/sinatra-chef-builder-plugin (master)
> $
>
> regards,
>
>
> On Fri, Jan 13, 2017 at 11:10 AM, Slide <slide.o....@gmail.com> wrote:
>
> Well, the SCM section doesn't match with the repo url:
>
> https://github.com/jenkinsci/sinatra-chef-builder-plugin is the repo URL,
> but the scm section has
>
>
> <connection>scm:git:git://github.com/jenkinsci/chefbuilder-plugin.git</
> connection>
>
> <developerConnection>scm:git:ssh://
> g...@github.com/jenkinsci/chefbuilder-plugin.git</developerConnection>
> <url>http://github.com/jenkinsci/chefbuilder-plugin</url>
> <tag>HEAD</tag>
>
> The URL's clearly don't match.
>
>
> The SCM section for the token-macro-plugin that I maintain is like this:
>
>
> <connection>scm:git:git://github.com/jenkinsci/token-macro-plugin.git</
> connection>
> <developerConnection>scm:git:g...@github.com:
> jenkinsci/token-macro-plugin.git</developerConnection>
> <tag>HEAD</tag>
>
> Can you post a build log of the current runs after the changes?
>
> On Fri, Jan 13, 2017 at 11:38 AM Irfan Sayed <irfu.sa...@gmail.com> wrote:
>
> Ok. thanks.
> Let me remove below line and commit.
> <hpi-plugin.version>1.106</hpi-plugin.version>
>
> so you mean, the curent scm section look OK?
> should i mention any username and password in the settings.xml?
> is mvn release:prepare release:perform command is enough?
>
> regards,
>
>
>
>
> On Fri, Jan 13, 2017 at 11:57 PM, Slide <slide.o....@gmail.com> wrote:
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVc%3DG7ze6tumj8YyWbO2yt3kPwaPp779s1407eqPV_QUyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to