public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Eugene Rozenfeld <erozen@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/microsoft/heads/main)] Add a workflow to package gcc
Date: Fri, 16 Apr 2021 20:36:11 +0000 (GMT)	[thread overview]
Message-ID: <20210416203611.100B23893662@sourceware.org> (raw)

https://gcc.gnu.org/g:338f73599e862eee9e24733e0c7b0904c67b2267

commit 338f73599e862eee9e24733e0c7b0904c67b2267
Author: Eugene Rozenfeld <erozen@microsoft.com>
Date:   Thu Nov 5 18:53:05 2020 -0800

    Add a workflow to package gcc

Diff:
---
 .github/workflows/package.yaml | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/.github/workflows/package.yaml b/.github/workflows/package.yaml
new file mode 100644
index 00000000000..8bec4006c54
--- /dev/null
+++ b/.github/workflows/package.yaml
@@ -0,0 +1,29 @@
+name: package-gcc
+
+# Disable for now since packaging needs to run after the build.
+# Run this workflow on every new commit
+# on: [push]
+
+jobs:    
+  package:
+    runs-on: ubuntu-18.04
+    steps:
+      - name: checkout
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+          submodules: recursive
+          lfs: true
+      
+     # This name step is needed for the Mariner build system because they look for the gcc-9.1.0 after the file is untarred  
+      - name: Rename gcc folder to gcc-9.1.0
+        run: mv gcc gcc-9.1.0
+          
+      - name: Package sources into tar
+        run: XZ_OPT=-e9T0 tar -cJf gcc-9.1.0.tar.xz gcc-9.1.0
+        shell: bash          
+      - name: upload artifact
+        uses: actions/upload-artifact@v2
+        with:
+          name: gccTar
+          path: gcc-9.1.0.tar.xz


                 reply	other threads:[~2021-04-16 20:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210416203611.100B23893662@sourceware.org \
    --to=erozen@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).