Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jenkins-install-jobs doesn't appear to be working #6

Closed
blakehall opened this issue Oct 31, 2013 · 2 comments
Closed

jenkins-install-jobs doesn't appear to be working #6

blakehall opened this issue Oct 31, 2013 · 2 comments

Comments

@blakehall
Copy link

Howdy,

I've run through the instructions in the README and I'm unable to get either changes to existing jobs or new jobs to install properly.

I have an almost completely vanilla setup:

Jenkins (ver. 1.537) running on localhost
node v0.10.21
grunt-cli v0.1.9
grunt v0.4.1

The job is embarrassingly simple:

<?xml version='1.0' encoding='UTF-8'?>
<project>
  <actions/>
  <description></description>
  <logRotator class="hudson.tasks.LogRotator">
    <daysToKeep>-1</daysToKeep>
    <numToKeep>7</numToKeep>
    <artifactDaysToKeep>-1</artifactDaysToKeep>
    <artifactNumToKeep>-1</artifactNumToKeep>
  </logRotator>
  <keepDependencies>false</keepDependencies>
  <properties/>
  <scm class="hudson.scm.NullSCM"/>
  <canRoam>true</canRoam>
  <disabled>false</disabled>
  <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
  <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
  <triggers/>
  <concurrentBuild>false</concurrentBuild>
  <builders>
    <hudson.tasks.Shell>
      <command>echo &apos;Howdy&apos;</command>
    </hudson.tasks.Shell>
  </builders>
  <publishers/>
  <buildWrappers/>
</project>

Hand editing the command and numToKeep values, the verify command shows a difference (as expected), but running install does not update jenkins.

Any suggestions to help debug what's going wrong here?

@sghill
Copy link
Owner

sghill commented Oct 31, 2013

Hey, thanks for checking out my project! Haven't solved this yet, but wanted to let you know I've seen it and could reproduce it.

I started by using curl to hit the endpoints that grunt-jenkins is using and that seems to be working fine, so we at least know it's not external. There isn't any verbose logging at the moment, and it looks like grunt has good support for that, so I'll probably start there.

Will circle back early next week.

@sghill
Copy link
Owner

sghill commented Nov 5, 2013

I've just pushed 0.4.0 to npm which should solve this issue.

In addition to the fix, you can use the --verbose flag to see the requests being sent to jenkins and the response codes coming back. This should make debugging easier, but happy to accept pull requests that make it better.

Thanks!

@sghill sghill closed this as completed Nov 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants