Re: [orbit-dev] Time for a new I-build?

[Roland Grunberg <rgrunber@xxxxxxxxxx>]

On Thu, 2017-04-13 at 10:00 +0200, Andreas Sewe wrote:
> Well, you can always test the preceding N-build prior to kicking off
> the
> I-build and test that -- provided that the build is reproducible and
> that changing the BUILD_LABEL doesn't have any deeper consequences.
> But
> I can see the argument for taking a step back, test once more, and
> only
> then make the repository available to the public by a deliberate
> action.
> 
> That being said, I don't see *where* you have to create the
> files.count
> file. Certainly not in the Git repository, as no such commit was made
> [1]. If such a file needs to be manually created on
> build|download.eclipse.org, it would be great if a Hudson job would
> exist that does that via a Shell script action, as not every Orbit
> committer may have SSH access to build.eclipse.org (I still have, but
> IIRC this is a legacy thing the admins like to phase out).

Yes, it's just a file that sits in the ${BUILD_LABEL}${TIMESTAMP}
folder of a promoted build so I'll just automate the HIPP that handles
promotion to do that.

-- 
Roland Grunberg