Issue 7640 in pharo: readme.txt at http://pharo.gforge.inria.fr/ci/script/README.txt points to the old ci server

Status: New
Owner: ----
Labels: Type-Bug

New issue 7640 by [hidden email]: readme.txt at  
http://pharo.gforge.inria.fr/ci/script/README.txt points to the old ci  
server
http://code.google.com/p/pharo/issues/detail?id=7640

its content is:

This directory contains a set of scripts to download the latest Pharo VMs
and Images.

The contents of this folder are stored in a git repository[1] and regularly
synched by a Jenkins job[2].

Examples:

        # Typically the scripts are curl'ed and directly piped to bash to avoid an
        # intermediate file:
        curl http://files.pharo.org/script/ciPharo20.sh | bash
       
        # Alternatively wget works as well:
        wget --quiet -O - http://files.pharo.org/script/ciPharo20.sh | bash

        # Each script comes with a help file describing the generated artifacts:
        wget http://files.pharo.org/script/ciPharo20.sh;
        bash ciPharo20.sh --help

[1] https://gitorious.org/pharo-build/pharo-build
[2] https://ci.inria.fr/pharo/job/Scripts-download/




--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Invalid

Comment #1 on issue 7640 by [hidden email]: readme.txt at  
http://pharo.gforge.inria.fr/ci/script/README.txt points to the old ci  
server
http://code.google.com/p/pharo/issues/detail?id=7640

no, all fine. the old one would be "ci.lille.inria.fr"

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Accepted

Comment #2 on issue 7640 by [hidden email]: readme.txt at  
http://pharo.gforge.inria.fr/ci/script/README.txt points to the old ci  
server
http://code.google.com/p/pharo/issues/detail?id=7640

=> We should remove the curl example. Curl doesn't handle the redirect from  
files.pharo.org, the rest should still work.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 7640 by [hidden email]: readme.txt at  
http://pharo.gforge.inria.fr/ci/script/README.txt points to the old ci  
server
http://code.google.com/p/pharo/issues/detail?id=7640

Yes, curl can follow redirects just fine:

curl -L http://files.pharo.org/script/ciPharo20.sh

;-)

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker