-
Notifications
You must be signed in to change notification settings - Fork 799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open source this action #7
Comments
False alert :| |
I also came looking for the source to see if Update: It does not. |
We are working towards this, our goal is for the community to be able to contribute fixes. |
@tedmiston You can use Action Outputs to do that, something like: - name: Get yarn cache
id: yarn-cache
run: echo "::set-output name=dir::$(yarn cache dir)"
- uses: actions/upload-artifact@v1
with:
path: ${{ steps.yarn-cache.outputs.dir }} Though for that specific case, you probably want to use |
Sharing an update regarding open-sourcing this action Sometime around Currently this action is a plugin on the runner where it has some extra permissions to do certain things. The majority of the work being done for open-sourcing this involves creating new APIs that will be able to interact with artifacts without being tightly-coupled with the runner. A new open-sourced NPM package will be created that will consume/interact with these APIs (similar to what we have for A lot of the top-requested issues/requests will be addressed such as #11 and #3. More information and specifics will be shared right around the launch of the |
Our runner was recently open-sourced. You can find all of the current code for Note: All the artifact code in the runner will eventually be removed once |
Will that code be moved to this repo when it is removed from there? |
The code will be split between this repo and a new one we are creating for the upcoming npm package. This action (along with |
Hope #14 will be also addressed in upcoming release as we forced to upload HTML pages to external host and there is no smart way to reference this data in embedded github checks - means need to looks throught stdout of step to find out a link. |
It appears it's not possible retain the execution permission, until mid-January actions/upload-artifact#7 (comment)
The The core functionality to interact with artifacts can be found in the This action now also uses Everything else is in this repo 😀 Moving forward it will be much easier to accept contributions and feedback once the preview is over. see: #62 |
You can now use it by using You can find all the core upload logic here or in the Artifact upload is now like a traditional typescript action and is no longer coupled to the runner. Moving forward it should be much easier to accept contributions and to add new features. |
* Extract k3s from docker image and publish it * Merge build+extract into single step * Remove k3s/ from artifact It appears it's not possible retain the execution permission, until mid-January actions/upload-artifact#7 (comment) * Re-add path as it's necessary * Add dockerignore * Attempt to rename k3s/ to bin/ * Create k3s-bin/k3s artifact * Update to k3s to v1.17.4+k3s1 * Change upload-artifact to v2 * Attempt to remove zip file * Update default version in README * Increase upload-artifact to v2 * Add artifact name and set executed permission
It is surprising that this repo (the scripts and documentation in this project) is licensed under MIT, since there is little to no relevant content to be licensed. However, I'm concerned about this from a practical point of view. I believe that most of the currently open issues (specially #3) could be fixed by the community, should we have any code to look at. It'd be really useful if the glue logic that gathers the artifacts and names them was open sourced, along with some minimal docs about the backend API that this action is using.
The text was updated successfully, but these errors were encountered: