Skip to content

Commit

Permalink
Fix instructions
Browse files Browse the repository at this point in the history 
As all jjb defintions are on gforcada's fork of jjb,
there's no need to put jenkins.plone.org in development mode at all.

Easier and merrier.
  • Loading branch information
@gforcada
gforcada committed Feb 15, 2015
1 parent 8a75596 commit 40c52cd
Showing 1 changed file with 0 additions and 9 deletions.
9 changes: 0 additions & 9 deletions docs/source/setup.rst
View file
Original file line number Diff line number Diff line change
Expand Up @@ -65,15 +65,6 @@ Put jenkins-job-builder in development mode::
$ cd src/jenkins-job-builder
$ python setup.py develop

Put this repository also on development mode::

$ cd ../.. # go back to the root
$ python setup.py develop

.. note::
Activate first jenkins-job-builder **and** later jenkins.plone.org so that
you don't end up with two versions of jenkins-job-builder on the virtualenv.

Test the jobs are properly setup::

$ jenkins-jobs --conf jenkins.ini.in test jobs.yml -o output
Expand Down

1 comment on commit 40c52cd

@gforcada
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tisto @bloodbare just a heads up, now that I merged 8a75596 you most probably need to fix your environment (well, actually I guess it will work, but just in case it doesn't, that's probably the reason :)

Please sign in to comment.