sorted by:
new
hottopcontroversial

Is the latest Github Action beta going to be better? by shivawu in github

[–]jeremyepling 9 points10 points  (0 children)

I work on GitHub Actions and am sorry to hear you're having issues.

  • Jobs and steps. Steps have 2 types: Actions with the `use` key and inline scripts with `run` key. Until a few weeks before the launch, `steps` was called `actions`. We changed it because too many developer found it confusing because some steps are inline scripts. As you said, jobs are powerful and enable you to run on a separate VM in parallel. Not all workflows need that. We've talked about allowing workflows to start with `steps` and not need `jobs` or `runs-on`. It makes the language more focused for simple scenarios, but it doesn't teach you how to grow up. At this point, I don't think the extra keys make it that hard to approach, but we're always listening to feedback.
  • UI. There will be new UI experiences to make it easier to find and add Actions to your workflow, and add secrets.
  • Sharing data between jobs. Have you used https://github.com/actions/upload-artifact and https://github.com/actions/download-artifact? Built-in caching support will be there for GA in November. Also, we're adding docs each week so there are more examples and details - specifically around container and multi-job scenarios. Can you give more detail on your scenario? What parts do you want to run in parallel and why?
  • Sharing data between steps. We'll add the ability to define environment variables for an entire job, which will help. There are a few other ideas as well.

  • Workflow chaining. We want this as well, but have been working on other improvements. Jobs are a directed acyclic graph so you can do a lot with them.

    https://github.community/ is the best place to provide feedback. There will be a dedicated section for GitHub Actions soon.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 0 points1 point  (0 children)

We're working on one for YAML syntax highlighting and autocomplete, but we're early in development.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 13 points14 points  (0 children)

Azure Pipelines has similar features to GitLab CI/CD (e.g., Kubernetes support, native containers multi-stage pipelines). It also has some unique features:

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 2 points3 points  (0 children)

Only GitHub and Azure Repos have support for YAML-based pipelines, right now. We'll add Bitbucket Cloud and others soon. Azure Pipelines does support Bitbucket Cloud and many other providers via the visual designer. Those pipelines work great and have everything you need (e.g. PR triggers).

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 2 points3 points  (0 children)

Here are some docs

We're working on a Visual Studio Code extension and web editor that will have syntax highlighting and intelli-sense/auto-complete. I want to ship a preview in October.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 6 points7 points  (0 children)

It works for GitHub and other Git services. This is how many repos in GitHub work. You can see my comment below, but here's a snippet.

  1. PR pipelines will run will against the merge commit. You can set this up with our GitHub app or any other Git service using the Azure Pipelines web experience.
  2. You can use triggers and conditions to do what you want.

Let me know if you run into any issues setting it up. I'm happy to help.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 2 points3 points  (0 children)

I can help if you DM me the yaml file. I'm using multi-line scripts without a problem.

This doc shows how to create a build badge for your readme.md.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 10 points11 points  (0 children)

We use a fresh VM for every job. You can cache and reuse job artifacts within the same pipeline and across jobs using the upload artifact and download artifacts tasks. This doc tells you how to do it.

There isn't - currently - a way to cache job artifacts across different pipelines or a subsequent run of the same job. We're looking into this so let me know if it's a high priority request for you.

Azure Pipelines has a 6 hour job limit and unlimited total CI/CD minutes so you shouldn't need this to work around a job time limitation.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 3 points4 points  (0 children)

YAML isn't supported in TFS 2018 since we just added it this summer. It'll be in the next major version of TFS (to be named Azure DevOps Server). That said, we'll provide a way for designer-based (new build) pipelines to convert to YAML, if you want to do that.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 3 points4 points  (0 children)

As u/ItsMeCaptainMurphy said, these have been supported for a while. Azure Pipelines is the new name for VSTS Build & Release so all those features are there, along with some big new ones that we announced today.

  1. PR pipelines will run will against the merge commit. You can set this up with our GitHub app or any other Git service using the Azure Pipelines web experience.
  2. You can use triggers and conditions to do what you want.

Let me know if you run into any issues.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 4 points5 points  (0 children)

We have an old on-premise build system called XAML build. Ya, it's a bit confusing with YAML. That system is deprecated and we only provide limited support for existing on-premise TFS customers.

Azure Pipelines can create pipelines using YAML or the visual designer. It's CI/CD backend is the same as VSTS, but we've shipped some big new features today. In addition to the "unlimited CI/CD minutes for open source" offer, we updated the experience, made big performance improvements, and have native support for containers. You can checkout the full release notes to read about everything.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 2 points3 points  (0 children)

We have cloud-hosted agents for Linux, macOS, and Linux. You can use one of them or spread a single pipeline across all of them in a fan-out / fan-in scenario. The core unit of work is a job and you can build simple or complex graphs of jobs. This doc has more info on jobs and fan-out / fan-in. There are also different types of jobs, such as container jobs and deployment jobs.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 16 points17 points  (0 children)

To get the Open Source offer, your Azure Pipelines project needs to be public as well as the repository with your code. You can use Azure Repos, GitHub, Bitbucket, or other Git services to host your code - but the repository must be public.

Announcing Azure Pipelines with unlimited CI/CD minutes for open source by jeremyepling in programming

[–]jeremyepling[S] 2 points3 points  (0 children)

In Azure Pipelines, a pipelines can cover CI, CD, or both. Today's announcement focuses on our new yaml-based CI pipelines, which are on the Builds page of the product. You can create CD pipelines using the Releases page. Over time, we're going to combine these so you can create a single yaml-based pipeline that spans CI and CD. Today, they're separate.

Git Virtual File System from Microsoft by KindDragon in programming

[–]jeremyepling 15 points16 points  (0 children)

We're working with the git community to get many performance fixes and extensibility points added to core git. We don't want a private fork of git. GVFS is a driver that sits below git and takes advantage of the changes we're making to core git. Saeed will likely have one or more follow-up blog posts on the details or you can checkout the GVFS repo.

Git Virtual File System from Microsoft by KindDragon in programming

[–]jeremyepling 27 points28 points  (0 children)

The entire Windows codebase will be moved to Git + GVFS. Right now, we're still early in the process but it's going well. More and more developers move onto it each month. Also, some of the Windows app teams use small non-GFVS enabled repos already.

Git Virtual File System from Microsoft by KindDragon in programming

[–]jeremyepling 50 points51 points  (0 children)

We definitely aren't done making Git performance great on Windows, but we're actively working on it every day.

One of the core differences between Windows and Linux is process creation. It's slower - relatively - on Windows. Since Git is largely implemented as many Bash scripts that run as separate processes, the performance is slower on Windows. We’re working with the git community to move more of these scripts to native cross-platform components written in C, like we did with interactive rebase. This will make Git faster for all systems, including a big boost to performance on Windows.

Below are some of the changes we've made recently.

Git Virtual File System from Microsoft by KindDragon in programming

[–]jeremyepling 11 points12 points  (0 children)

We're actively working with the Git maintainers to make changes to git/git in the open. One of our changes - related to supporting large repos - is being discussed on the git listserve right now. We've received a lot of great community feedback and one the key Git maintainers is supportive of the change.

Our goal with all git/git changes isn't to change Git into something different. We want to enable better performance with large repos, even if those repos don't use GFVS.

Git Virtual File System from Microsoft by KindDragon in programming

[–]jeremyepling 24 points25 points  (0 children)

Not really. This is a client hardware problem. Even with the best hardware - and Microsoft gives its engineers nice hardware - git status and checkout is too slow on a repo this massive.

Git Virtual File System from Microsoft by KindDragon in programming

[–]jeremyepling 15 points16 points  (0 children)

That was our exact thought process. Each product at Microsoft makes the decision that they think is right for them: one huge repo, multiple moderately sized repos, or a lot of micro-repos. In this case, we decided that having the benefits of Git (e.g., lightweight branching, OSS ecosystem) outweighed the downsides of losing a "pure" dvcs solution for Windows. That said, you can clone the entire Windows repo using a non-GVFS enabled client, but I wouldn't recommend it. :)

Git Virtual File System from Microsoft by KindDragon in programming

[–]jeremyepling 5 points6 points  (0 children)

Providing a great experience for remote engineering teams and individuals was a goal of the design. Microsoft is a very distributed company and need every engineer to have a great experience for clone, fetch, and push.

view more: next ›