Skip to main content
search
Category

Community

Jan 31
Love0
early-bird talks cdCon 2023

cdCon 2023 Sneak Peek: Five Early-bird Talks Accepted

By Blog, Community

Contributed by: Lori Lorusso, JFrog, cdCon Program Committee Chair

The cdCon Call for Papers is well underway and, based on the submissions the program committee just reviewed, this year’s cdCon is going to be jam-packed with amazing technical content and community-focused sessions from project maintainers, end users, and notables in the continuous delivery space. With over 40 submissions received in just a week we were hard-pressed to choose just five to announce early but without further ado… check out the first five early bird talks:

Panel: The Continuous Delivery Paradox – Balancing Business Value with Speed
Moderator: Gautham Pallapa, VMWare

Fidelity’s Software Delivery Platform – Frictionless Approach To Achieve Autonomic DevOps & Enhanced Security/Compliance Practices
Speakers: Jamie Plower & Evan Elms, Fidelity Investments

Operating Tekton with Secure Defaults
Speakers: Christie Wilson (Warwick) &  Wendy Dembowski, Google

CI/CD for Data – Building Dev/Test Data Environments with Open Source Stacks
Speaker: Vinodhini Duraisamy, Treeverse

Trusted Open Source Artifacts on the Blockchain: A Hands-On Introduction to Pyrsia
Speaker: Adam Gardner, Dynatrace

Congratulations to the speakers of these talks! 

*If you weren’t a part of the first five – have no fear, you are still in the running for acceptance into the cdCon 2023 program. We will send out notifications for the remaining program on March 3, 2023.* 

Submit Your Talk

The CFP deadline is Friday, February 10 at 11:59 PM PST and we need more submissions to review so we can curate the best content to help others on their path to continuous delivery. We’re looking for talks in the following tracks:

  • 101 (beginners to the CDF & continuous delivery content)
  • Interoperability in CD
  • Cloud Native CD
  • Progressive Delivery
  • Best Practices in Continuous Delivery
  • MLOps
  • Observability & Analytics
  • Performance
  • Security & Supply Chain Security
  • Developer Experience & Productivity
  • Platform Engineering
  • Policy & Governance
  • Automation & Testing
  • Leadership
  • Community & Culture

Don’t miss this great opportunity to share your knowledge with the CDF community. 

Submit your Talk

Have Questions? – Ask The Committee

Our Program Committee members are your resource if you have any questions during the submission process. Each member brings their own experience in continuous delivery to the table and we are here to help you if you need help with your abstracts. Please feel free to reach out to me on the CDF Slack Channel, Twitter, or LinkedIn and I can help connect you to one of our members that would be best suited to answer your questions. 

  • Adam Kaplan (Red Hat)
  • Alyssa Tong (CloudBees)
  • Andrew Fong (Prodvana)
  • Batuhan Apaydın (Trendyol)
  • Brad McCoy (Basiq)
  • Carlos Panato (Chainguard)
  • Dadisi Sanyika (Apple)
  • Garima Bajpai (Ericsson)
  • Lori Lorusso (JFrog) – Program Committee Chair
Jul 13
Love0
help wanted sign

Help Wanted: Intent-Based Pipelines

By Blog, Community

Contributed by Justin Abrahms, eBay

Drawing a software delivery pipeline is a task that takes a couple of developers 30 minutes and a whiteboard.

We start our build, we do some testing, try it out in staging and… when we’re happy… publish it to production. Going from there to a working pipeline that’s modeled in the way that you want either requires a large framework investment that’s likely company-specific (Amazon, Google), using a SaaS provider (CloudBees, CircleCI), or writing a bunch of Kubernetes YAML / Bash scripts.

At the Interoperability SIG, we’ve been discussing what it might look like to have a simplified DSL for expressing the outcomes of a pipeline, without getting so tied into the mechanisms of telling the system how to do it. This is an illustrative (but not particularly battle-hardened) example:

meta:
  # Channel which will get updates on deploys. One message for each release and
  # Information in the thread as it progresses through the pipeline.
  slackChannel: myapp-deploys

  # Who to complain to when this breaks.
  owners: your-ldap-or-equivalent-group-here

build:
  # Explicitly not setting up a jenkins instance. Framework should do this, if necessary.
  type: docker
  # ...or...
  # command: mvn package

deploy:
  default:  # These apply to all stages below, unless they're overridden
    cores: 100m
    memory: 300Mb
    ramp:
      # deploy to 1% then 10% then 100% as a rollout strategy. There will be
      # a few options available.
      rolloutStrategy: ONE_TEN_ALL
      bakeTime: 5m
  dev:
    rollout:
      regions: dev-west-1a
  staging:
    rollout:
      regions: dev-west-1a
  prod:
    rollout:
      regions: prod-west-1a, prod-west-1b, prod-west-2a, prod-west-2c
      # Starting from 1, deploy to 2x the regions of the last deploy, so 1,2,4,8,16.
      strategy: GEOMETRIC
    approvals:
      - metricsValidator:
          promql: sum(increase(failure[5m])) > 5
          onResults: rollback

Something like the above would allow us to simplify the expression of what we want the shape of our pipeline to be, but without having to become experts in Tekton or Argo or any of the other great tools for accomplishing this. This will hopefully allow more developers to engage with CI/CD pipelines and have a more active role in the quality of their software.

Join the Conversation

If this sounds like something you’re interested in, we’d love to discuss it with you during one of our regular, open-to-anyone meetings or give #sig-interoperability a ping in slack.

Close Menu