It appears that the foundation hudson doesn¹t have the ³trunk² part of the
url indicated in the document which was causing the 404s. The proper url
format is:
https://hudson.eclipse.org/hudson/job/[job name]/lastSuccessfulBuild/
>From what I can tell, you can either have the system return you an XML
document, a JSON fragment, or executable python code that builds the object
structure for python scripts. So far it looks like the procedure is going
to be something like:
1. Build finishes in hudson archiving the build artifacts locally and making
them available through this remote API
2. A custom application is triggered via cron tab that accesses this API and
retrieves the general build information
3. The information is processed and the appropriate artifacts are retrieved
via HTTP from the hudson server and copied locally
4. Once the download is verified (not sure how this will be done), the local
file is then published to the downloads directory path on the build server
for mirroring.
The application run on build.eclipse.org is going to have to be far more
intelligent and capable than earlier ant/bash script incarnations as the
information must be parsed from a formatted document. It will also be more
difficult as we¹ll need to reproduce the add/remove/update features already
present in the original cbi scripts. Am I missing something that would make
this process less complex? What do you guys think?
Trip
On 9/22/10 12:53 PM, "Terran Gilman" <t...@openmethods.com> wrote:
> I¹m not sure what the proper approach is here. I have read the remote access
> article before. I have attempted to access that url scheme for some of the
> projects that appear to have successfully built but always get a 404 for the
> last successful url. Even if this is working, is the suggestion to download
> what resides at that location to build.eclipse.org, and then copy it to the
> mirrored drive location so it can be copied again to the live download areas?
>
> It took a significant amount of time for me to figure out how to get the
> provisioning to work after migrating to buckminster. I guess if I have to
> re-invest this time so be it, but some other project has to have already
> figured this out on the new server. I¹d hate to duplicate my previous work
> and their current work reinventing the wheel.
>
> Trip
>
>
> On 9/22/10 12:46 PM, "Miles Parker" <milespar...@gmail.com> wrote:
>
>>
>> Is there a standard approach to this and/or should we come up with one before
>> everyone rolls their own (as we all seem wont to do)? :)
>>
>> On Sep 22, 2010, at 10:39 AM, Nicolas Bros wrote:
>>
>>> You can access the archive from the Hudson build using Hudson's REST API :
>>> http://wiki.hudson-ci.org/display/HUDSON/Remote+access+API
>>> And then copy it to the downloads area.
>>>
>>> On Wed, Sep 22, 2010 at 7:23 PM, Trip Gilman <t...@openmethods.com> wrote:
>>>> With the new build server being in a separate location from the Hudson
>>>> server, what is the new process of getting the product of a Hudson build
>>>> over to the downloads area?
>>>>
>>>> Trip
>>>>
>>>>
>>>>
>>>> On 9/17/10 5:54 PM, "David Carver" <d_a_car...@yahoo.com
>>>> <http://d_a_car...@yahoo.com/> > wrote:
>>>>
>>>>> Build.eclipse.org <http://Build.eclipse.org/> has died....they are
>>>>> building a new build.eclipse.org <http://build.eclipse.org/> , they can
>>>>> make it stronger, they can make it faster, they have the technology.....
>>>>>
>>>>> http://en.wikipedia.org/wiki/The_Six_Million_Dollar_Man
>>>>>
>>>>> Dave
>>>>>
>>>>> On 09/17/2010 02:54 PM, Miles Parker wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Looks like both build servers are down now as well..
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sep 17, 2010, at 12:20 PM, David Carver wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> build.eclipse.org <http://build.eclipse.org/>
>>>>>>> <http://build.eclipse.org <http://build.eclipse.org/> > is currently
>>>>>>> down, see cross project message regarding it.
>>>>>>>
>>>>>>>
>>>>>>> Dave
>>>>>>>
>>>>>>> On 09/17/2010 12:03 PM, Miles Parker wrote:
Excellent..I'm eager to try it out. However..
On Sep 17, 2010, at 10:34 AM, Trip Gilman wrote:
>
> I couldn¹t get the actual command as I can¹t seem to connecto to
> build.eclipse.org <http://build.eclipse.org/> <http://build.eclipse.org/> .
> Is it down right now or am I having issues?
>
I can't get to it either, but then I'm always having issues.. :)
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org <http://dash-dev@eclipse.org/>
https://dev.eclipse.org/mailman/listinfo/dash-dev
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> dash-dev mailing list
>>>>>>> dash-dev@eclipse.org <http://dash-dev@eclipse.org/>
>>>>>>> https://dev.eclipse.org/mailman/listinfo/dash-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> dash-dev mailing list
>>>>>> dash-dev@eclipse.org <http://dash-dev@eclipse.org/>
>>>>>> https://dev.eclipse.org/mailman/listinfo/dash-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> dash-dev mailing list
>>>>> dash-dev@eclipse.org <http://dash-dev@eclipse.org/>
>>>>> https://dev.eclipse.org/mailman/listinfo/dash-dev
>>>>
>>>> _______________________________________________
>>>> dash-dev mailing list
>>>> dash-dev@eclipse.org
>>>> https://dev.eclipse.org/mailman/listinfo/dash-dev
>>>>
>>>
>>>
>
>
> _______________________________________________
> dash-dev mailing list
> dash-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
