Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] PTP inclusion in Kepler RC build

Moving to cross-project list, since this comes up every now and then, so will serve as a good reminder for everyone ... even if PTP has some project specific issue.


First, the aggregation build won't pick up anything automatically ... IF there are no other "builds" triggered. And there are two ways to trigger a build:  either a b3aggrcon file changes, or someone manually pushes the "schedule a build" button (anyone who can commit to simrel.build, should be able to trigger a build ... if you log in to Hudson with committer Id).

But, pretty sure there were aggregation builds on Wednesday, triggered by other people, so should have been picked up then. So might be some other issue, Perhaps your content.xml/jar file or composite wasn't updated?

I recommend, though, if anyone changes the contents of a repo, but do not change aggregation files, that you manually trigger your own build, just to make sure there is a build after your contribution, so you can check all is as you expect.

Let me know if I can help further,





From:        Beth Tibbitts <beth@xxxxxxxxxx>
To:        David M Williams/Raleigh/IBM@IBMUS,
Cc:        Greg Watson <g.watson@xxxxxxxxxxxx>
Date:        02/10/2014 04:58 PM
Subject:        PTP inclusion in Kepler RC build
Sent by:        bethtib@xxxxxxxxx




David,
We had a glitch last week, not critical, but want to make sure we get it right this week.

Last week's Kepler RC2 build didn't pick up the ptp build we had in place by tuesday afternoon.
We are a +3/Wednesday build  for Kepler (moving back to +2/Tuesday for Luna) so shouldn't it have picked it up without any trigger/fileChange?

(It *is* in the same location as the previous M build, we don't have a different dir name for each M/RC build like we did for the R release)

We don't have alot of changes going into Kepler SR2 so this particular one isn't critical
but want to make sure we get this week's build in ok
I'll watch closer on Tuesday night (remind me the URL where the repository gets assembled) but just wanted to ask
in case we're missing something, want time to fix it.

Thanks.
I thought it was in place by Tuesday afternoon Feb 4...and i thought i saw that it was... now the dir list below has me wondering...
but even if it wasn't there by 14:55 on Feb 5, wouldn't it be picked up? (Maybe nobody else triggered one after that, and we didn't have a trigger?)

btibbitts@build:~/downloads/tools/ptp/builds/kepler/milestones/SR2> ls -la
total 128332
drwxrwsr-x 4 gwatson tools.ptp      4096 Feb  5 14:54 .
drwxrwsr-x 7 gwatson tools.ptp      4096 Feb  5 14:55 ..
-rw-r--r-- 1 gwatson tools.ptp      7489 Feb  4 19:40 artifacts.jar
-rw-r--r-- 1 gwatson tools.ptp     56620 Feb  4 19:40 content.jar
drwxr-sr-x 2 gwatson tools.ptp      4096 Feb  4 19:40 features
drwxr-sr-x 2 gwatson tools.ptp     32768 Feb  4 19:40 plugins
-rw-rw-r-- 1 gwatson tools.ptp 131159106 Feb  5 14:54 ptp-master-7.0.4.201402042359.zip   (for our use only, not needed for repo)



...Beth

Beth Tibbitts
beth@xxxxxxxxxx

Back to the top