Hi Eduard,

I would check the trigger settings in the job, particularly which "type"
of pattern matching is being used for the branches. Found it tends to be
the spot that catches most people out when configuring jobs with the
Gerrit Trigger plugin. If you're looking to trigger against all branches
then you would want "Type: Path" and "Pattern: **" appearing in the UI.

If you have sufficient access using the 'Query and Trigger Gerrit
Patches' page accessible from the main view will make it easier to
confirm that your Jenkins instance can actually see changes in gerrit
for the given project (which should mean that it can see the
corresponding events as well). Can also use the same page to re-trigger
for PatchsetCreated events to see if you've set the patterns on the job
correctly.

Regards,
Darragh Bailey

"Nothing is foolproof to a sufficiently talented fool" - Unknown

On 08/12/14 14:33, Eduard Matei wrote:
> Resending this to dev ML as it seems i get quicker response :)
>
> I created a job in Jenkins, added as Build Trigger: "Gerrit Event:
> Patchset Created", chose as server the configured Gerrit server that
> was previously tested, then added the project openstack-dev/sandbox
> and saved.
> I made a change on dev sandbox repo but couldn't trigger my job.
>
> Any ideas?
>
> Thanks,
> Eduard
>
> On Fri, Dec 5, 2014 at 10:32 AM, Eduard Matei
> <eduard.ma...@cloudfounders.com
> <mailto:eduard.ma...@cloudfounders.com>> wrote:
>
>     Hello everyone,
>
>     Thanks to the latest changes to the creation of service accounts
>     process we're one step closer to setting up our own CI platform
>     for Cinder.
>
>     So far we've got:
>     - Jenkins master (with Gerrit plugin) and slave (with DevStack and
>     our storage solution)
>     - Service account configured and tested (can manually connect to
>     review.openstack.org <http://review.openstack.org> and get events
>     and publish comments)
>
>     Next step would be to set up a job to do the actual testing, this
>     is where we're stuck.
>     Can someone please point us to a clear example on how a job should
>     look like (preferably for testing Cinder on Kilo)? Most links
>     we've found are broken, or tools/scripts are no longer working.
>     Also, we cannot change the Jenkins master too much (it's owned by
>     Ops team and they need a list of tools/scripts to review before
>     installing/running so we're not allowed to experiment).
>
>     Thanks,
>     Eduard
>
>     -- 
>
>     *Eduard Biceri Matei, Senior Software Developer*
>     www.cloudfounders.com
>     <http://www.cloudfounders.com/> | eduard.ma...@cloudfounders.com
>     <mailto:eduard.ma...@cloudfounders.com>
>      
>
>      
>     *CloudFounders, The Private Cloud Software Company*
>      
>     Disclaimer:
>     This email and any files transmitted with it are confidential and
>     intended solely for the use of the individual or entity to whom
>     they are addressed.If you are not the named addressee or an
>     employee or agent responsible for delivering this message to the
>     named addressee, you are hereby notified that you are not
>     authorized to read, print, retain, copy or disseminate this
>     message or any part of it. If you have received this email in
>     error we request you to notify us by reply e-mail and to delete
>     all electronic files of the message. If you are not the intended
>     recipient you are notified that disclosing, copying, distributing
>     or taking any action in reliance on the contents of this
>     information is strictly prohibited.  E-mail transmission cannot be
>     guaranteed to be secure or error free as information could be
>     intercepted, corrupted, lost, destroyed, arrive late or
>     incomplete, or contain viruses. The sender therefore does not
>     accept liability for any errors or omissions in the content of
>     this message, and shall have no liability for any loss or damage
>     suffered by the user, which arise as a result of e-mail transmission.
>
>
>
>
> -- 
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
> <http://www.cloudfounders.com/> | eduard.ma...@cloudfounders.com
> <mailto:eduard.ma...@cloudfounders.com>
>  
>
>  
> *CloudFounders, The Private Cloud Software Company*
>  
> Disclaimer:
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed.If you are not the named addressee or an employee or
> agent responsible for delivering this message to the named addressee,
> you are hereby notified that you are not authorized to read, print,
> retain, copy or disseminate this message or any part of it. If you
> have received this email in error we request you to notify us by reply
> e-mail and to delete all electronic files of the message. If you are
> not the intended recipient you are notified that disclosing, copying,
> distributing or taking any action in reliance on the contents of this
> information is strictly prohibited.  E-mail transmission cannot be
> guaranteed to be secure or error free as information could be
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> contain viruses. The sender therefore does not accept liability for
> any errors or omissions in the content of this message, and shall have
> no liability for any loss or damage suffered by the user, which arise
> as a result of e-mail transmission.
>
>
> _______________________________________________
> OpenStack-Infra mailing list
> openstack-in...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to