# 0.19.RC1 and Plugins

**URL:** <https://discuss.elastic.co/t/0-19-rc1-and-plugins/6629>\
**Category:** Elasticsearch\
**Created:** [February 7, 2012, 11:34pm UTC](https://discuss.elastic.co/t/0-19-rc1-and-plugins/6629 "2012-02-07T23:34:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_smith/32/1323_2.png) [@Paul\_Smith](https://discuss.elastic.co/u/Paul_Smith)\
**Post date:** [February 7, 2012, 11:34pm UTC](https://discuss.elastic.co/t/0-19-rc1-and-plugins/6629/1 "2012-02-07T23:34:46Z")

</div>

Heya,

I have an Jenkins automated build that on commit of a new ES version #  
automatically downloads and builds RPM's for use in our environment. I  
went to update to 0.19.RC1 but got a failure because the plugins located  
here:

[http://elasticsearch.googlecode.com/svn/plugins/river-\*](http://elasticsearch.googlecode.com/svn/plugins/river-*)

Do not have a matching 0.19.RC1 build. This has been working in the past  
since 0.17 land. Is this a change in 19 to not update these plugins at the  
same time. ? (if so I'll amend the script), but just checking.

tah,

Paul Smith

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [February 7, 2012, 11:37pm UTC](https://discuss.elastic.co/t/0-19-rc1-and-plugins/6629/2 "2012-02-07T23:37:24Z")

</div>

Plugins have moved to their own repo, so you need to explicitly install them (from github), with the respective version they are at. For example, the cloud-aws plugin is located at: [GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch](https://github.com/elasticsearch/elasticsearch-cloud-aws), and you install it with:

bin/plugin -install elasticsearch/elasticsearch-cloud-aws/1.3.0

On Wednesday, February 8, 2012 at 1:34 AM, Paul Smith wrote:

> Heya,
> 
> I have an Jenkins automated build that on commit of a new ES version # automatically downloads and builds RPM's for use in our environment. I went to update to 0.19.RC1 but got a failure because the plugins located here:
> 
> [http://elasticsearch.googlecode.com/svn/plugins/river-](http://elasticsearch.googlecode.com/svn/plugins/river-)\*
> 
> Do not have a matching 0.19.RC1 build. This has been working in the past since 0.17 land. Is this a change in 19 to not update these plugins at the same time. ? (if so I'll amend the script), but just checking.
> 
> tah,
> 
> Paul Smith

---

<div class="post-metadata">

**Author:** ![Barsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barsk/32/13734_2.png) [@Barsk](https://discuss.elastic.co/u/Barsk)\
**Post date:** [February 13, 2012, 12:54pm UTC](https://discuss.elastic.co/t/0-19-rc1-and-plugins/6629/3 "2012-02-13T12:54:59Z")

</div>

Shay Banon skrev 2012-02-08 00:37:

> Plugins have moved to their own repo, so you need to explicitly  
> install them (from github), with the respective version they are at.  
> For example, the cloud-aws plugin is located at:  
> [GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch](https://github.com/elasticsearch/elasticsearch-cloud-aws), and you  
> install it with:
> 
> bin/plugin -install elasticsearch/elasticsearch-cloud-aws/1.3.0

How do you know which plugin version goes with which ES version?

/Kristian

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [February 13, 2012, 6:21pm UTC](https://discuss.elastic.co/t/0-19-rc1-and-plugins/6629/4 "2012-02-13T18:21:31Z")

</div>

Each plugin on the elasticsearch github org includes a table showing which version works with what. I recommend for other plugins to do the same. Here is a sample: [GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch](https://github.com/elasticsearch/elasticsearch-cloud-aws).

On Monday, February 13, 2012 at 2:54 PM, Kristian Jörg wrote:

> Shay Banon skrev 2012-02-08 00:37:
> 
> > Plugins have moved to their own repo, so you need to explicitly  
> > install them (from github), with the respective version they are at.  
> > For example, the cloud-aws plugin is located at:  
> > [GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch](https://github.com/elasticsearch/elasticsearch-cloud-aws), and you  
> > install it with:
> > 
> > bin/plugin -install elasticsearch/elasticsearch-cloud-aws/1.3.0
> 
> How do you know which plugin version goes with which ES version?
> 
> /Kristian

---

<div class="post-metadata">

**Author:** ![derrickburns](https://avatars.discourse-cdn.com/v4/letter/d/50afbb/32.png) [@derrickburns](https://discuss.elastic.co/u/derrickburns)\
**Post date:** [February 14, 2012, 12:27am UTC](https://discuss.elastic.co/t/0-19-rc1-and-plugins/6629/5 "2012-02-14T00:27:54Z")

</div>

Would you be willing to share (open source) the Jenkins code that is not  
confidential or specific to your application?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:39am UTC](https://discuss.elastic.co/t/0-19-rc1-and-plugins/6629/6 "2017-07-06T03:39:33Z")

</div>


