Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
I think pip installing locally to connect to a cluster is something people
would want to use - but if people disagree then cutting down the artifacts
makes sense and I'm happy to do that in a
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15659
The use case I intended for this one was to allow installing Spark on a
laptop against some local file system, not using pip as a distributed mechanism
across a cluster. For that use case I think
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
For the same reasons we have this in the current download, we could of
course limit this to a smaller subset of you want.
On Mon, Nov 28, 2016 at 5:29 PM Reynold Xin
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15659
@holdenk why are we introducing so many tarballs for Python?
```
[ ] pyspark-2.1.0+hadoop2.3.tar.gz 2016-11-28 20:17165M
[TXT]
Github user minrk commented on the issue:
https://github.com/apache/spark/pull/15659
Awesome, thanks @holdenk!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Yay! :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/15659
Agreed, so I'm going to cherry-pick this into branch-2.1.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
@JoshRosen thank you so much! That's awesome. I've had some off-line chats
about why I think we should merge this for 2.1 as well (hopefully @rxin can
chime in here with his thoughts) but I think
Github user rgbkrk commented on the issue:
https://github.com/apache/spark/pull/15659
ð Thank you everyone!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/15659
I'm going to merge this to master now and will look into cherry-picking to
branch-2.1.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
cc @jkbradley / @davies / @JoshRosen / @rxin - it seems like this should be
an ok state to merge if one of you has the bandwidth? I'd really like to get
this in before we cut RC1.
---
If your
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
I'v added the extra exclusion rules for extra safety in packaging :) cc
@rxin if this looks good to merge?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68669/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68669 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68669/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68669 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68669/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Ping @joshrosen / @rxin :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
@JoshRosen - yes since we ship the jars with them we want people to be able
to install the correct package for the hadoop distribution they are running
with/against.
---
If your project is set up
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68638/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68638 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68638/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68638 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68638/consoleFull)**
for PR 15659 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/15659
> I think we will want to keep the release-build tagging so that the
artifacts are correct for the different hadoop versions.
Ah, so the idea is that we'll make separate PyPi artifacts
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68619/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68620/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68619 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68619/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68620 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68620/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68620 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68620/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68619 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68619/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
@JoshRosen: So I took a look at doing that on the flight and I think we
will want to keep the release-build tagging so that the artifacts are correct
for the different hadoop versions, but we can
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Thanks @JoshRosen I'll take a crack at that this weekend :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/15659
I just tested this out end-to-end on my Mac and it worked great. I have
only one minor concern that I'd like to fix regarding the `version.py` file:
Today, the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68570/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68570 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68570/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
and or @rxin?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68570 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68570/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
So @joshrosen or @davies now that I've updated the shell scripts does this
look good to go?
I'll make a follow up to maybe add shellcheck to our standard linting if
it's something we want
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Jenkins retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user minrk commented on the issue:
https://github.com/apache/spark/pull/15659
Sounds great!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68557/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68557 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68557/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68557 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68557/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
So the simplest thing sounds like updating the error message, for now I'll
avoid changing the maven build since that might have some unintended collateral
effects and this change is currently
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68554/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68554 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68554/consoleFull)**
for PR 15659 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68553/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68553 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68553/consoleFull)**
for PR 15659 at commit
Github user minrk commented on the issue:
https://github.com/apache/spark/pull/15659
> Any ideas on how we could follow up and support that install pattern?
To go all the way to the two commands I expected to work based on Python
tradition:
```bash
./build/mvn
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Thanks @JoshRosen for taking time to review this. The factoured out fix is
at https://github.com/apache/spark/pull/15860 :)
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68554 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68554/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
@minrk thanks :) Any ideas on how we could follow up and support that
install pattern?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68553 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68553/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
@joshrosen Is `shellcheck` intended to be part of our standard linting?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user minrk commented on the issue:
https://github.com/apache/spark/pull/15659
I downloaded this branch and ran this to test (macOS, Python 3.5):
```bash
build/mvn -DskipTests clean package
cd python
python setup.py sdist
pip install dist/*.tar.gz
```
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Yay! Thanks @JoshRosen :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/15659
I can aim to take a review pass this afternoon or this weekend.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Maybe @jkbradley ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68532/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68532 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68532/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Thanks @davies :)
I think at this point we've probably got things pretty well covered
(@viirya & @nchammas also have done a lot of review and @minrk took a look at
the initial PR /
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68532 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68532/consoleFull)**
for PR 15659 at commit
Github user davies commented on the issue:
https://github.com/apache/spark/pull/15659
This looks good to me in general, but did not check all the details.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Also like if there is any testing or anything I can do or coordinate to get
done that would help y'all feel comfortable with this please let me know :)
---
If your project is set up for it, you
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
So @davies does this look ok? It would be nice to get this in before RC1 is
cut so that it can have the pip artifacts for people to test as well. (cc
@rxin).
---
If your project is set up for it,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68490/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68490 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68490/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68490 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68490/consoleFull)**
for PR 15659 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68447/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68447 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68447/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68447 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68447/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Jenkins retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68419/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68419 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68419/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
Jenkins retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68419 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68419/consoleFull)**
for PR 15659 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68407/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68407 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68407/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
re-ping to @davies & @rxin
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68407 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68407/consoleFull)**
for PR 15659 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68372/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68372 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68372/consoleFull)**
for PR 15659 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68370/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68370 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68370/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
ping @davies / @rxin / @mateiz - I'm getting a flight tomorrow if you
happen to have any comments beforehand I can try and address them during the
flight :)
---
If your project is set up for it,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68372 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68372/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68370 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68370/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
@davies - no this does also address SPARK-18129 take a look at the changes
inside of `dev/create-release/release-build.sh` :)
---
If your project is set up for it, you can reply to this email and
1 - 100 of 251 matches
Mail list logo
