Ok ... thanks for the detail. I suspect I did make a (perfectly logical :) 
change that Gerrit doesn't quite know how to interpret. :/ 

I have "changed it back" ... and I don't see a build starting right away 
.. so, my apologies, but can you try "touching" your patch set (or, what 
ever the right terminology is) and we'll see if it now works after my 
"revert" in the configuration. 

Thanks, 




From:   Jeff Johnston <[email protected]>
To:     Cross project issues <[email protected]>, 
Date:   06/05/2015 01:19 PM
Subject:        Re: [cross-project-issues-dev] Trying to submit a change 
to simrel and   no gerrit validation
Sent by:        [email protected]



I made a commit for master on org.eclipse.simrel.build.  I then pushed
to gerrit as I always do by pushing to: my remote in .git/config:

[remote "review"]
        url = 
ssh://[email protected]:29418/simrel/org.eclipse.simrel.build.git
        push = HEAD:refs/for/master

This creates a gerrit review:

https://git.eclipse.org/r/#/c/49543/

but it did not start the validate job.  I tried retriggering by changing 
the commit log
and again, no validate.  I even tried adding Hudson CI as a reviewer which 
was a last
attempt hack.  Again, no build started.

I just changed my password as I was getting warning messages from Eclipse, 
but I wouldn't
think that would affect ssh access.

-- Jeff J.

----- Original Message -----
> Should work. But let's go over basics.
> 
> When you say your "project's Gerrit validator" do you mean the Sim Rel 
job
> called
> simrel.mars.runaggregator.VALIDATE.gerrit
> I don't think so, since it has not ran at all for 18 hours, but, just in 
case
> you do, you still need to "submit" a change to put
> the change into the master branch.
> 
> Second, did you actually change a file in the org.eclipse.simrel.build 
Git
> repository?
> If so, I don't see it in the log, but that (changing something in 
master) is
> what "triggers" the simrel.mars.runaggregator.VALIDATE job.
> 
> It does does not run periodically, and it does not run based on changes 
in
> project's repositories.
> 
> If you mean you have a change in your project repository, you can either
> change your b3aggrcon file, or, you can
> (after logging in to that Hudson instance) use the web interface to 
start
> your own build in simrel.mars.runaggregator.VALIDATE.
> 
> Hudson checks every 15 minutes if there has been a change to files in
> o.e.simrel.build.
> 
> Hope that clears it up (if not, please ask again).
> 
> 
> 
> 
> 
> 
> From: Jeff Johnston <[email protected]>
> To: Cross project issues <[email protected]>,
> Date: 06/04/2015 07:56 PM
> Subject: [cross-project-issues-dev] Trying to submit a change to simrel 
and
> no gerrit validation
> Sent by: [email protected]
> 
> 
> 
> 
> I'm trying to submit a change to org.eclipse.simrel.build in preparation
> for RC4, but the validator build isn't starting. Is there some reason 
for
> this? My project's gerrit validator is working fine.
> 
> -- Jeff J.
> _______________________________________________
> cross-project-issues-dev mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe 
from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> 
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe 
from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to